DEVICE CAMMING2

The camming, is a technique applicable to motion control servo axes and allows you to solve applications where one or more slave axes have spaces, uneven, too staying in sync with respect to the position of a reference axis called “master”. The master axis can be a real or virtual axis (the master simulated).
Typical applications are:

• Cuts and processes on the fly, both linear and circular, on plastic, sheet metal, cardboard.
• Packaging in place of mechanical cams.
• In the winding of cable, wire, etc. with wiring-guide.
• In textiles and in feeding the “grinding machine” for layering of fabrics or pasta.
• In screen printing or flexo printing plates.
• In the lines of “transport product” for spacing and/or synchronization of the materials movement.

The absolute position that must assume the slave axis is always expressed as a function of position absolute master axis and this Association is placed in a specific table called “cam table”.
The “cam table” consists of 40 sectors; each sector consists of: CodeG = operating instruction of the sector in use.
CodeQm = incremental position of the master, in units; are accepted only positive increments.
CodeQs = incremental position of the slave, in units; both positive and negative increments are accepted.
CodeM = general numeric code that can be used by the PLC logic.
CodeQma = special operating instructions auxiliary master quota used.
CodeQsa = special operating instructions auxiliary slave used quota.

The codeG operative instructions associated with each sector of the cam, you can be defined how motion law (acceleration, deceleration, constant speed…) the slave axis must move along the space established in codeQs at the same time as the master runs through the space defined as codeQm.
Until the master is moving at constant velocity, the space covered by the master axis is directly proportional to the time spent and the codeQs e codeQm spaces being always defined in the same amount of time even the law of motion applied to the slave axis, within the sector, is applicable in direct proportion to the space covered by the master in the sector; the master and the slave are therefore linked in space between them.
If the speed constant chosen for the master is the maximum you can evaluate immediately what the maximum accelerations, decelerations and speeds that will be the slave axis.
This procedure allows you to formulate the law of motion of the slave axis as a function of time to evaluate the dynamic performance required by your application and then apply the the same law of motion as a function of space covered by the master during the execution of the cam.
To simplify the calculation of the absolute positions of the master and the slave It is assumed that the master is moving at a constant speed whereby the axes positions can be represented in a Cartesian diagram Speed / Time. Below is a simple example of compiling the “cam table”.

In order to can run a cam as in the example, you have to fill in the “cam table” as follows:

QEM is available to help customers in the of the “cam table” compilation.
The device can be divided into two main parts:
A slave axis positioner with trapezoidal or selectable planetary ramps. A nalog cam manager.
Basic block diagram is as follows:

In the configuration file (.CNF), the BUS section must be declared so that they are present the hardware resources required for the implementation of the device CAMMING2. There must be at least two bidirectional counter and a 16-bit resolution analog output. In the INTDEVICE section of the .CNF file must be to add the following definition:

;-------------------------------
; Internal device declaration
;-------------------------------
  INTDEVICE
 
        <DEVICE_NAME> CAMMING2 TCAMP COUNTS COUNTM INTL IAZERO INTLM
 
                          IAZEROM ING INGINT IOUTA OUT

Where:

You take as an example a CAMMING2 device configured as in the START-UP and with parameterisation of the axis (set-up) already written.
The task is first initialized the device and then run a interrupt input which shows its status on an exit.
The task will be carried out:

;-------------------------------------
; CAMMING2 device management
;-------------------------------------
INIT AxisX                      : Initializes the axis
WAIT AxisX:st_init              ; Wait until the axle is initialized
LOOPON AxisX                    ; Hooks the control loops
WAIT AxisX:st_loopon            ; Wait for the axis has hooked the
                                ; control loops
CALOFF AxisX                    ; Exit from calibration
                                ; of the axis
WAIT NOT AxisX:st_cal           ; Wait until the device is not in
                                ; calibration
CNTUNLOCK AxisX                 ; Unlocks the master counter
WAIT NOT AxisX:st_cntlock       ; Wait until the counter master is
                                ; unlocked
CNTDIR AxisX                    ; Sets the right direction of increase
                                ; slave counter
WAIT NOT AxisX:st_cntrev        ; Wait until the slave counter is
                                ; set in the sense of increase
CNTUNLOCKM AxisX                ; Unlocks the master counter
WAIT NOT AxisX:st_cntlockm      ; Wait until the counter master is
                                ; unlocked
CNTDIRM AxisX                   ; Sets the right direction master
                                ; counter increment
WAIT NOT AxisX:st_cntrevm       ; Wait until the counter master is
                                ; set in the sense of increase
REGON AxisX                     ; Unlock the adjusting
WAIT NOT AxisX:st_regoff        ; Wait for the regulation unlocking
 
MAIN:
 
IF AxisX:st_int                 ; If the interrupt line is active
  AxisX:funOut = 2              ; activates output
ELSE
  AxisX:funOut = 1              ; disables the output
ENDIF
 
ENDIF                           ; END
 
WAIT 1
JUMP MAIN
END

The CAMMING2 device did not has within it the cntratio parameter, but let the installer ability to work with unfinished encoder resolutions by setting the data as space covered in a round encoder (measure) and number of pulses/round encoder (pulse).
The relationship between measure and pulse is the encoder resolution and must have values between 1 and 0.000935.

• The measure paramenter is placed in units without decimal points (for example 100.0 millimeters is inserted 1000 tenths of a millimeter).
  
• The pulse parameter is inserted 4 encoder bitrate (for example if connected an encoder with 1024 pulses round, is inserted 4096, If the measure is calculated on a encoder round).

You have to control a rotating table that have the accuracy of 0,1° with the 1024 pulses round encoder mounted directly to the motor; you will set the following values:
measure = 3600
pulse = 4096

If for the selected unit of measure is also provided for the presence of a decimal point positions must be represented as an integer and represent space on the drive measurement without decimal point. The resolution must be calculated using the same method and in the parameter measure the magnitude without decimal point. The decimal point will then be inserted into the representation of the value-time viewers (ex. as properties in the HMI). This parameter can take 0÷3 values.

The speeds are always expressed in whole units of measure in the unit of time choice. From this it emerges that the device must know the location of the decimal point of the unit of measure and this is done with the decpt parameter.

This section describes only the use of a number of some commands; for descriptions of all the set commands, refer to the following chapters.
The two main controls are what give start and break execution of cam: STARTCAM and STOPCAM. There are also a series of commands dedicated to emergency response, the loop control, START and STOP the axis.

TheSTARTCAMcommand, the slave axis attaches to master and will follow the trend described in the cam always starting from the first sector. You cannot take a STARTCAM during the execution of the (st_camex = 1) cam; ihis control is left to the programmer.
The cam will pop out automatically if it encounters a END instruction or you can stop it in flight by using the STOPCAM.

If the cam is running (st_camex = 1), Once received the STOPCAM command the slave axis is released immediately by the master, brings his speed to zero following the deceleration ramp set (tdec parameter) and remaining in reaction to space. The deceleration ramp is asynchronous with respect to the master.

At the START command, the slave axis is positioned to the dimension declared in the setpos variable with the speed set in setvel; the placement will run using the acceleration ramp set in tacc parameter and the deceleration ramp set in parameter tdec. The type of ramp used (trapezoidal or epicicloidal) is inserted in the ramptype parameter.

If during the placement (not during the execution of a cam) you must stop the axis with a deceleration ramp, It will simply give theSTOP command the axis decelerates to a stop with the ramp in the tdec parameter.

When positioning it is possible to vary the speed of the axis without affecting the location to get to. This can lead to an increase or a decrease in velocity, even in several places of the same positioning. This is accomplished with new writing in the setvel parameter. No gear is always available except during the deceleration ramp and is reported (st_chvel = 1)

When positioning can be varied even acceleration/deceleration times. For example, the device can start a placement at a rate very short and once they reach the speed set, varied tacc parameter and executed a change of speed with a very long ramp.
For special applications and trapezoidal ramps, ramp time can be varied even during a change of speed, in this case the new time is put into execution immediately.

This command puts the axis in emergency conditions; the st_emrg state is set to one. If the emergency command is sent to the axis during a placement, movement is stopped without deceleration ramp, the analog output will be set to zero volts and you dropped the reaction of space. If the cam is active (st_camex = 1), the movement is interrupted without deceleration ramp, the analog output will be set to zero volts, space reaction is released and the cam (st_camex = 0).
With st_emrg = 1 (emergency condition), you cannot move the axis.

This command will reset the emergency condition; the axis comes in reaction to space and waits for a command to be able to move (does not automatically resume interrupted positioning).

The LOOPOFF command removes the reaction of space without stopping the axis. With st_loopon = 0 the axis handling axis commands but accepts all placements will be performed without reaction of space.
A placement made reaction loop-free is comparable to a positioning run without proportional gain (is not guaranteed to arrive in position).

The LOOPON command closes the ring of space without stopping the axis. With st_loopon= 1 the axis is moved using the P.I.D. control features.

Following is a table summarizing the conditions necessary for the axis in reaction to space and to perform placements.

The epicicloidal motion is used to move the axes without sudden variations of speed. The time of positioning of an axis moved by trapezoidal ramps is the same compared to the same axis moved by epicicloidal ramps, but ramps vary the shear rate (acceleration) with up to half of the ramp itself.
For comparison shows the difference of the development of the acceleration in the two cases: with linear ramp (trapezoidal) and with ramp reducers.

The same goes for the deceleration ramp.
Planetary movement has the ability to behave in different ways in the event of a reduction in profile (rtype) and in the case of stop during acceleration (stopt) If the cam is not running (st_camex = 0).

	The profile reduction is used only if you are doing a placement and not if you're running a cam (st_camex = 0).

If the cam is not running (st_camex = 0) and space to go is less than that which allows to reach the speed set by the acceleration and deceleration ramps, you pass in the phase called “profile reduction”.
You can keep fixed the time of ramps, decreasing gradients of the ramps and the speed in proportion (rtype parameter set to 0).

You can also decrease the time of the ramps while maintaining the gradient of constant acceleration and decrease speed in proportion (rtype parameter set to 1).

With the rtype parameter set to 0 xtend considerably the time needed to placements with loss of productivity of the machine, instead of setting it to 1 in case of short placements shorter, but keeping the constant gradient you lose the beneficial effect of the epicicloidal action.

	The type of sleep while the ramps is only used if you are doing a placement and not if you're running a cam (st_camex = 0).

In the event that the cam is not running (st_camex = 0) and we should curb the axis during acceleration with STOP commnand You must choose whether to complete the flight, or if you want to abort the flight and consequently change the epicicloidal action.
In case you set the stopt parameter to 0 is first completed the acceleration ramp and then performed the deceleration ramp.

In case you set the parameter stopt to 1 stops the acceleration ramp and started immediately the deceleration ramp set.

You immediately notice that there is a substantial difference between the setting of stopt to 0 or to 1. To make the choice of what type of stop use, one must remember that in case of emergency stop the emergency command exists that instantly locks and without ramp positioning.

	Before starting actual placements you must make sure that electrical connections and mechanical appliances have not cause malfunctions.

For the management of the axis, the device uses a ± 10 V analogue output range and 16-bit signed resolution; this calibration function with analog output can be driven with a constant value in order to test links and functionality.

• Remove the emergency condition with the RESUME command.
• The state st_emrg = 0
• Enable calibration axis status with the CALON command; the st_cal state must therefore be 1.
• You can now set the analog voltage with the vout parameter; the value is expressed in tenths of volt (-100 ÷ 100 = -10 ÷ 10 V). It is recommended to introduce low values (5, 10, 15… equal to 0.5, 1, 1,5 V).
• When the axis is moving the frq parameter indicates the frequency in Hz of the sphases of the transducer.
• The posit parameter that displays the position varies indicating the space covered by the axis. If setting a positive voltage will count decrements, it is necessary to invert the phases of the transducer or reverse the direction in driving.
• You can reverse the direction of the count using the CNTREV command.
• If with output voltage to zero the axis is not stationary, adjust the offset parameter to correct the voltage until movement does not stop. The input value (each bit corresponds to 0.3 mV), will be added algebraically to the value of the analogue output; This operation allows to compensate for any drift of electronic component, both in QMOVE outgoing and to driver input. The value is expressed in bits with sign.
  For an optimal result of calibration this operation must be performed with the system to temperature capacity.
• To disable calibration status send the CALOFF command.
• The state st_cal = 0

The device generates the voltage value of the analogue output based on a ratio between the maximum velocity of the axis and the maximum output voltage. Proportionality is obtained with the maxvel parameter, that represents the speed of the axis on the analog voltage (10 V). Obviously the axle must behave symmetrical analog voltage to zero, therefore the speed must be the same on both the positive and negative voltage at maximum.
Prior to determining the value of maximum velocity,we must establish the unit of time to use for the representation of the speed in the device; the unitvel parameter defines the unit of time of speed (Um/min or Um/s).

The theoretical method is a calculation that was performed on the basis of maximum motor speed. Once established the maximum revolutions per minute that are declared in the motor, We get the maximum velocity is expressed in the unit of measure the unit of time chosen.
Enter the maximum velocity value calculated in the maxvel parameter.

The practical approach is based on the reading of the speed detected by the device in the vel parameter, giving the drive a known voltage. To provide the voltage to drive the device should be placed in a position of calibration as described in the previous paragraph. If the system permits, give the drive a voltage of 10 V and read the speed value in the vel parameter. If, on the other hand, provides a part of the output voltage (1, 2, … 5 V), calculate the maximum velocity with a proportion.
Enter the value found by maximum velocity in the maxvel parameter.

	Before handling the Board, check the proper operation of emergency equipment and protection.

The procedures described here have allowed us to complete the first phase of parameterizing device. Now you can run simple movement of the axis.

• Move the axis in a position whereby it can fulfill a certain area without touching the maximum and minimum quota limits.
• Set the current position to zero axis, by setting the parameter posit = 0.
• Set up the parameters that define the position of the limit switches software: minpos = 0 and maxpos the value of the maximum stroke of the axis.
• Set the parameter that defines the axis time to reach the maximum speed tacc = 100. This parameter is expressed in hundredths of a second (100 = 1 sec.)
• Set the speed of positioning with the setvel parameter.
• Set the target quota with the setpos parameter.
• Set the parameter feedfw = 1000 (100%)
• If the device is in emergency state (st_emrg = 1) give the RESUME command.
• Start positioning with the START command. To stop the movement give the EMRG command.

This first movement was done without speed feedback space. The placement may have been executed with some error introduced by the non-linearity of the components or an imperfection in the calibration of the maximum speed. Enabling space feedback this error goes away.

The placement runs in the preceding paragraph has been made without considering any position errors.
To check the correct position of the axis in continuously and automatically, You must have the position feed-back; for this reason introduces the control algorithm PID + FF including proportional shares, integral, derivative and feed-forward; the value of the analog output is given by the summation of feed forward, proportional, derivative and integrative actions.
This section describes a series of actions to adjust the parameters that affect this control.
In order to achieve a satisfactory adjustment is sufficient to use only the actions feedforward and proportional; integral and derivative actions are used only for adjustments under special conditions.

The feed-forward helps make the system more ready on placements, providing the analogue output voltage proportional to the theoretical speed of positioning. In practice it is the component which you performed the placements of the previous chapter.
The contribution of this action can be adjusted with the parameter feedfw; This parameter is expressed as 1/1000 speed theoretical portion; so, to introduce such as 98.5% you must set 985 (thousandths).

This action provides an output proportional to the instantaneous axis position error. The extent of the proportional action is defined by the pgain parameter that defines the sensitivity of the system.
The pgain parameter is introduced in thousandths; the unit value of the gain (1000) provides an analog output to maximum value (10 V) concerning the maximum speed error. For maximum speed error means the space taken by axis - at the maximum speed - for the duration of the sampling time of the device.

Integrates the position error of the system over time set in integt parameter updating the release until the error is not canceled.
If it drops the integration time of the error, the system retrieves the error faster, but can become unstable, tending to swing.

Anticipates the change of the motion of the system by delete the overshoot positioning. The size of change is calculated over time set in derivt parameter.
When the time of derivation of error is higher, more faster is the transient error recovery system, but if you enter a value that is too high the system becomes unstable, tending to fluctuate.

In order to move the slave axis must first declare the parameterization of axis. Once this stage is thought to want to move the slave axis with jog manuals using Inp01 input for moving forward and the Inp02 input to move it back.
As an example, consider a device configured as in START UP. The task is first initialized the device and then run the manual jog.

;----------------------------------------------------
; Manual jog management
;----------------------------------------------------
 
INIT AxisX                          : Initializes the axis
WAIT AxisX:st_init                  ; Wait until the axle is initialized
LOOPON AxisX                        ; Hooks the control loops
WAIT AxisX:st_loopon                ; Wait for the axis has hooked the
                                    ; control loops
CALOFF AxisX                        ; Exit from calibration
                                    ; of the axis
WAIT NOT AxisX:st_cal               ; Wait until the device is not in
                                    ; calibration
CNTUNLOCK AxisX                     ; Unlocks the master counter
WAIT NOT Axis:st_cntlock            ; Wait until the counter master is
                                    ; unlocked
CNTDIR AxisX                        ; Sets the right direction of increase of
                                    ; slave counter
WAIT NOT AxisX:st_cntrev            ; Wait until the counter is slave
                                    ; set in the sense of increase
CNTUNLOCKM AxisX                    ; Unlocks the master counter
WAIT NOT AxisX:st_cntlockm          ; Wait until the counter master is
                                    ; unlocked
CNTDIRM AxisX                       ; Sets the right direction of increase of
                                    ; master counter
WAIT NOT AxisX:st_cntrevm           ; Wait until the counter master is
                                    ; set in the sense of increase
REGON AxisX                         ; Unlock the adjusting
WAIT NOT AxisX:st_regoff            ; Wait the unlocked of the regulation
MAIN:
 
IF Inp01 AND Inp02                  ; If the Inp01 and the
                                    ; Inp02 inputs are active
  IF NOT AxisX:st_still             ; If the axis is not stationary
    STOP AxisX                      ; Stop the axis
  ENDIF
ENDIF
 
IF Inp01 AND NOT Inp02              ; I the Inp01 input is
                                    ; active and the
                                    ; Inp02 input are deactivate
  IF AxisX:st_still                 ; If the axis is stopped
    AxisX:setvel=AxisX:maxvel/10    ; I set the speed of
                                    ; manual movement
    MANFW AxisX                     ; Forward manual
  ENDIF
ELSE
  IF NOT Inp02                      ; If the Inp02 input
                                    ; is deactive
    IF NOT AxisX:st_still           ; If the axis is not stationary
       STOP AxisX                   ; Stop the axis
    ENDIF
  ENDIF
ENDIF
 
IF Inp02 AND NOT Inp01              ; If the Inp02 input
                                    ; is active and the Inp01
                                    ; input is deactivate
  IF AxisX:st_still                 ; If the axis is stopped
    AxisX:setvel=AxisX:maxvel/10    ; I set the speed of
                                    ; manual movement
    MANBW AxisX                     ; Backward manual
  ENDIF
ELSE                                ; Otherwise
  IF NOT Inp01                      ; If the Inp01 input is
                                    ; deactive
  IF NOT AxisX:st_still             ; If the axis is not stationary
     STOP AxisX                     ; Stop the axis
  ENDIF
ENDIF                               ; END
 
WAIT 1
JUMP MAIN
END

The device does not have inside datagroup or array data where you can contain various types of cams, so, if you need to manage different cams according to the type of work, you must place the CPU tools and download data on the device whenever there is a need.

Example:
This example handles the cam programming with data entered in the second program of a datagroup. The device is configured as described in the startup.

;--------------------------------------------------
; Configuration file
;--------------------------------------------------
 
;--------------------------------------------------
; Global Variables
;--------------------------------------------------
 
GLOBAL
gfProgram F ;Enabling cam programming
 
;--------------------------------------------------
; System Variables
;--------------------------------------------------
 
SYSTEM
sbPuntProg B ;Program number that you want to put into execution
 
;--------------------------------------------------
; Datagroup Variables
;--------------------------------------------------
 
DATAGROUP
dgCamma
 
DATAPROGRAM 10 ;10 available programs
ddlCode L ;program code
 
STEP 128 ;128 available program step
ddbCodeG B ;G code
ddlCodeQs L ;Qs code
ddlCodeQs L ;Qm code
ddlCodeM L ;M code
ddlCodeQma L ;auxiliary Qm code
ddlCodeQsa L ;auxiliary Qs code
 
;--------------------------------------------------
; Cam programming tasks
;--------------------------------------------------
MAIN:
   .
   .
   sbPuntProg = 2 ;Setting the program pointer
   .
   .
 
;--------------------------------------------------
; Programming of the CAMMING2 device
;--------------------------------------------------
IF gfProgram
   AxisX:codeG1     = ddbCodeG [sbPuntProg , 1] ;Sector 1
   AxisX:codeQm1    = ddlCodeQm [sbPuntProg , 1] ;Sector 1
   AxisX:codeQs1    = ddlCodeQs [sbPuntProg , 1] ;Sector 1
   AxisX:codeQma1   = ddlCodeQma [sbPuntProg , 1] ;Sector 1
   AxisX:codeQsa1   = ddlCodeQsa [sbPuntProg , 1] ;Sector 1
   AxisX:codeM1     = ddlCodeM [sbPuntProg , 1] ;Sector 1
   AxisX:codeG2     = ddbCodeG [sbPuntProg , 2] ;Sector 2
   AxisX:codeQm2    = ddlCodeQm [sbPuntProg , 2] ;Sector 2
   AxisX:codeQs2    = ddlCodeQs [sbPuntProg , 2] ;Sector 2
   AxisX:codeQma2   = ddlCodeQma [sbPuntProg , 2] ;Sector 2
   AxisX:codeQsa2   = ddlCodeQsa [sbPuntProg , 2] ;Sector 2
   AxisX:codeM2     = ddlCodeM [sbPuntProg , 2] ;Sector 2
 
   .
   .
 
   AxisX:codeG128 = ddbCodeG [sbPuntProg , 128] ;Sector 128
   AxisX:codeQm128 = ddlCodeQm [sbPuntProg , 128] ;Sector 128
   AxisX:codeQs128 = ddlCodeQs [sbPuntProg , 128] ;Sector 128
   AxisX:codeQma128 = ddlCodeQma [sbPuntProg , 128] ;Sector 128
   AxisX:codeQsa128 = ddlCodeQsa [sbPuntProg , 128] ;Sector 128
   AxisX:codeM128 = ddlCodeM [sbPuntProg , 128] ;Sector 128
 
   gfProgram = 0
ENDIF

The CAMMING2 device manages cam sectors scheduled incremental, within which shows the space ahead from the master and the space to take the slave. A cam is composed of several sectors which may be accelerating, decelerating, or dedicated to operations such as speed change, for example, the power factor correction counter or loop cam.
Each sector of the cam must contain information about:

• codeG sector type
• codeQm master quota (Attention: insert only positive values)
• codeQs slave quota
• codeQma auxiliary master quota (Attention: insert only positive values)
• codeQsa auxiliary slave quota
• codeM Code of general use, which is indicated by the codeMex variable. Typically contains the tools the state, cam special states, etc.

The sector of acceleration is used with slave axis stopped (slave zero speed, regardless of the speed of the master); at the end of the sector the speed of the slave is the same as that of the master.
Typical cases of acceleration are shown in A, B, C and D pictures.
In the example of A picture, at the end of the sector to be equal to that of the speed of the slave master; the law that binds the space master and slave is:
Slave space = 1/2 Master space
More smaller will be the space master considered more greater will be the acceleration gradient of the slave, which we can derive from the formula:
Time acc. slave = Master space in the sector of acc. / Maximum master speed

	In case you are facing this kind of acceleration we recommend using codeG = 132 code.

Picture A

Programming example:

• codeG 132
• codeQm Master space
• codeQs Slave space
• codeQma Not used
• codeQsa Nont used
• codeM generic code

	If you wish to use the planetary ramps, we recommend the use of the codeG = 232 code.

In case you want to use the epicicloidal ramps to accelerate with the same functions described for 132 sector, simply program the sector as described above and planning codeG = 232.

In the example of B picture, at the end of the field the speed of the slave is in proportion to the speed of the master (the proportion will be called K), the law that binds the master and slave space space is:
Slave space = K/2 Master space
More smaller will be the space master who considers, more greater will be the acceleration gradient of the slave, that we can derive from the formula:
Time of slave acc. = Master space in the acc. sector / Maximum speed master

	In case you are faced with this type of acceleration is required using codeG = 131 code.

Picture B

Programming example:

• codeG 131
• codeQm Master space
• codeQs Slave space
• codeQma Not used
• codeQsa Not used
• codeM generic code

	If you wish to use the epicicloidal ramps, we recommend using codeG = 231 code.

In case you want to use the epicloidal ramps to accelerate with the same functions described for 131, simply program the field as described above and planning codeG = 231.
In the picture C example, more acceleration are needed, and you cannot set Master/Slave quotes of finished value. 150 sector is basically the sum of two sectors: 131 and 133. This sector is used when you know the spaces next to the field of acceleration and you want one slave very small accelerative space, even less than the unit of measurement.
The sector 150 uses the following parameters:

• codeG : sector code (150)
• codeQma : master space within which the slave must be at a certain speed, which we call the synchronization.
• codeQm and codeQs : where the division indicates the relationship between the slave and master (synchronization report). These spaces will be made after accelerative section.
• codeQsa : indicates the space into encoder pulses that must take the slave in the acceleration phase to reach the sync speed.
  More smaller will be the space master who considers himself, more greater will be the acceleration gradient of the slave, who do we get from the formula:
  Time of Slave acc. = Master space on the acc. sector / Maximum master speed

	In case you are faced with this type of acceleration is required using code codeG = 150.

Picture C

Programming example:

• codeG 150
• codeQm Master Space
• codeQs Slave Space
• codeQma Master Space in acceleration
• codeQsa Slave SPace in acceleration (bit * 4)
• codeM generic code

In the picture D example, more acceleration are needed, and you cannot set Master/Slave quotes of finished value. 152 sector is basically the same the sector 131. This sector is used when you know the synchronization report and you want one slave very small, even smaller than the space inertial measurement unit.
152 sector takes advantage of the following parameters:

• codeG : sector code (152)
• codeQma : master space within which the slave must be at a certain speed, which we call the synchronization.
• codeQm and codeQs : where the division indicates the relationship between the slave and master (synchronization report).
• codeQsa : indicates the space into encoder pulses that must take the slave in the acceleration phase to reach the sync speed.
  More smaller will be the space master who considers himself, more greater will be the acceleration gradient of the slave, who do we get from the formula:
  Time of Slave acc. = Master space on the acc. sector / Maximum master speed

	In case you are faced with this type of acceleration is required using code codeG = 152.

Picture D

Programming example:

• codeG 152
• codeQm Master Coefficient
• codeQs Slave Coefficient
• codeQma Master Space in acceleration
• codeQsa Slave Space in acceleration (bit * 4)
• codeM generic code

	If you wish to use the epicicloidal ramps, we recommend the use of the code codeG = 252.

In case you want to use the epicicloidal ramps to accelerate with the same functions described for 152 sector, simply program the sector as described above and planning the code codeG = 252.

In case you need to stop the slave axis (regardless of its speed), remaining engaged with the cam (zero speed regardless of the speed of the master), it can be used the deceleration sector.
In the picture E example, at the end of the sector, the speed of the slave will be zero; la law that binds the space master and slave (the proportion between the master and the slave speed will be called K) is:
Slave space = K/2 Master space
More smaller is the space master who considers himself, more greater will be the degree of deceleration of the slave, which you can obtain from:
Time of Slave dec. = Master space in the dec. sector / Maximum master speed

	In case you find yourself in front of a deceleration is obligatory the use of the code codeG = 135.

Picture E

Programming example

• codeG 135
• codeQm Master space
• codeQs Slave space
• codeQma Not used
• codeQsa Not used
• codeM generic code

	If you wish to use the epicicloidal ramps, we recommend the use of the code codeG = 235.

In case you want to use the epicicloidal ramps to accelerate with the same functions described for the sector 135, simply program the field as described above and planning codeG = 235.

In the picture F example, syou need strong deceleration, and you cannot set Master/Slave dimensions of finished value. The 151 sector is basically the sum of two sectors: 133 and 135. This sector is used when you know the spaces before the deceleration area and want a space decelerativo slave very small, even smaller than the unit of measurement.
151 sector makes use of the following parameters:

• codeG : sector code (151)
• codeQma : master space within which the slave must be from a certain speed, which we call the zero speed synchronization.
• codeQm and codeQs : where the division indicates the relationship between the slave and master (synchronization report). These spaces are made before decelerative section.
• codeQsa : indicates the space into encoder pulses that must cover the slave during deceleration.

More smaller is the space master who considers himself, more greater will be the degree of deceleration of the slave, which we can derive from the formula:
Time of Slave dec. = Master space in dec. sector / Maximum master speed

Picture F

Programming example

• codeG 151
• codeQm Master space
• codeQs Slave space
• codeQma Master space decelerating
• codeQsa Slave space in decelerating (bit * 4)
• codeM generic code

	In order to do this operation there are two types of codes (codeG = 133 and codeG = 134) which differ only in the choice of the speed that you want to give to the slave at the end of the speed change sector.

Speed change sector can be used:

• Whenever the slave axis must reach speeds (nonzero), starting at a different speed (also non-zero).
• Whenever the slave axis must maintain a constant speed.

In the example the speed of the slave is the same as that of the master (at the beginning of speed change sector). In case the speed is different you need to consider, in the follow formulas, the master and slave relationship of constant speed at the beginning of the sector.
The codeG = 133 provides that the speed of the slave at the end of the sector can be different from the initial and final speed of the slave (of end time sector), will depend exclusively on the master/slave relationship of spaces (see picture G).
We have three cases:
1)Master/slave relationship < 1 Speed of the slave at the end of the sector > of the master speed
2)Master/slave relationship = 1 Speed of the slave at the end of the sector = of the master speed
3)Master/slave relationship > 1 Speed of the slave at the end of the sector < of the master speed

The speed at the end of the sector is given by the formula:
Slave Speed = Master Speed + { [ 2 (Slave Space - Master Space) / Master Space ] x 100 } %

Picture G

Programming example:

• codeG 133
• codeQm Master Space
• codeQs Slave Space
• codeQma Not used
• codeQsa Not used
• codeM generic code

	If you wish to use the epicicloidal ramps, we recommend the use the code codeG = 233.

In case you want to use the epicicloidal ramps to accelerate with the same functions described for the sector 133, simply program the sector as described above and planning codeG = 233.
The codeG = 134 provides that the speed of the slave at the end of the sector is the same as the speed at half the slave sector will depend exclusively on the relationship of the master/slave spaces (see picture H). We have three cases:
1 Master/slave relationship < 1 Speed of the slave in the middle of the sector > of the master speed
2 Master/slave relationship = 1 Speed of the slave in the middle of the sector = of the master speed
3 Master/slave relationship > 1 Speed of the slave in the middle of the sector < of the master speed

The speed in the middle of the sector will be given by the formula:
Slave Speed = Master Speed + { [ 2 (Slave Space - Master Space) / Master Space ] x 100 } % x (Master Speed)

Picture H

Programming example:

• codeG 134
• codeQm Master Space
• codeQs Slave Space
• codeQma Not used
• codeQsa Not used
• codeM generic code

	If you wish to use the epicicloidal ramps, we recommend the use the code codeG = 234.

In case you want to use the epicicloidal ramps to accelerate with the same functions described for the sector 134, simply program the sector as described above and planning codeG = 234.
If you are programming a sector 133, 134, 233 or 234 with master and slave space to 0, it is considered as a non-operating sector (codeG = 130).
In the picture I example, wants to change speed to the slave, and it is not possible to set a Master/Slave relationship of finite value. The sector 153 is the same as sector 133. This sector is used when you know the synchronization report and you want one slave very small inertial space, sometimes even lower than the unit.
The sector 153 uses the following parameters:

• codeG : sector code (153)
• codeQma : master space within which the slave must be at a certain speed, which we call the synchronization.
• codeQm and codeQs : whose division indicates the ratio between the slave and master (rapporto di sincronizzazione).
• codeQsa : the device indicates the space in which the slave route encoder pulses to reach the sync speed after acceleration phase.

	In case you are using this type of transmission speed, we recommend the use of the code codeG = 153.

Picture I

Programming example:

• codeG 153
• codeQm Master Coefficient
• codeQs Slave Coefficient
• codeQma Space Master in acceleration
• codeQsa Space Slave in acceleration (bit * 4)
• codeM generic code

	If you wish to use the epicicloidal ramps, we recommend the use the code codeG = 253.

In case you want to use the epicicloidal ramps to accelerate with the same functions described for the sector 153, simply program the sector as described above and planning codeG = 253.

In the example of L picture, you want to bring the slave at a speed without having to run a connection ramp. The sector 154 unlike all other, forces the initial velocity equal to the final speed while maintaining a constant speed between two points. This sector can be used as the starting sector of the cam (starting without acceleration), as intermediate sector or final sector (stop without ramp).
The sector 154 uses the following parameters:

• codeG : sector code (154)
• codeQma : Softening sector type
• codeQm and codeQs : whose division indicates the relationship between the slave and master (synchronization relationship). These spaces are performed during the sector.
• codeQsa : if set to 0 indicates that the next sector is an area of movement, if set to 1 indicates that the next sector does not provide for movement (deceleration with zero ramp).

	In case you have to use this type of movement is obligatory the use of the code codeG = 154.

Picture L

Programming example:

• codeG 154
• codeQm Master Space
• codeQs Slave Space
• codeQma Softening sector type
• codeQsa
  0 = next sector of movement
  1 = stationary axis in the next sector
  2 = Gearing axis
• codeM generic code

Many times there is a need to start the slave on the master known, but there is the possibility to connect to a proximity sensor. The only constraint is that the sector containing the codeG 160 must be the first sector of cam motion and cannot be placed in the loop. At the STARTCAM command, the st_camex state goes to 1 and the the movement of the Slave axis begins only at Master quota (expressed in units of measurement) set in the sector 160 and from there will follow the trend described in the following sectors.
If the STARTCAM command is given with the above-quota master count, is set the warning 9; under these conditions the Master counting must become less than the quota set for it to be in the right situation of the system.
You can't get into a sector with codeG = 160 coming from a jump or a loop cam (error 7).

Programming example:

• codeG 160
• codeQm STARTCAMMA quota expressed in units of measurement
• codeQs Not used
• codeQma Not used
• codeQsa Not used
• codeM Not used

The exchange end cam sector (codeG = 136), is used whenever one has to conclude the cam (disengage the cam) stopping the slave axis in reaction to space on the last point of the cam. The slave axis must be stopped at the time of the release of the cam, pwhereby it is assumed that the previous sector contains the code of the deceleration (codeG = 135).
After this area the cam is released and, to reattach it, you have to send the STARTCAM command.

Programming example:

• codeG 136
• codeQm Not used
• codeQs Not used
• codeQma Not used
• codeQsa Not used
• codeM Not used

The absolute jump sector (codeG = 137), is used to jump to a sector (defined in the codeQm) in order to change the fly cam performance according to the conditions established by the programmer.
The most common situation for using this feature is that a portion of the cam that needs to be repeated several times.
Keep in mind that the counts are not updated, and then in the long run can go into overflow. Therefore, use the update count fields in the field that precedes the one containing the codeG = 137.

Programming example:

• codeG 137
• codeQm Sector number to jump
• codeQs Not used
• codeQma Not used
• codeQsa Not used
• codeM Not used

The conditional jump sector (codeG = 190), is used to make a jump to a sector (defined in the codeQm) for a number of times (defined in the codeQs) after that you move on to the next sector. The count of the number of the jumps performed is available in codeQma.
Care must be taken that the counts are not updated, and then in the long run can go into overflow. Therefore, use the update count sector in the field that precedes the one containing the codeG = 190.

Programming example:

• codeG 190
• codeQm Sector number to jump
• codeQs Number of times
• codeQma Jump number viewing
• codeQsa Not used
• codeM Not used

The loop sector cam (codeG = 138), is used to repeat the cam running from the sector number one, eliminating by removing both master and slave counts.
We recommend using this code in repeated endlessly cams that have no problems with subtraction of counts.

Programming example:

• codeG 138
• codeQm Not used
• codeQs Not used
• codeQma Not used
• codeQsa Not used
• codeM Not used

The not operative sector (codeG = 130), is used to reserve areas to perform functions only under special conditions defined by the programmer.
For example you may consider a cam for the flying saw, in which you have to reserve the sectors to be used in case, mechanically, you cannot make the cut master space reserved for this operation.

Programming example:

• codeG 130
• codeQm Not used
• codeQs Not used
• codeQma Not used
• codeQsa Not used
• codeM Not used

All sectors that require no space master to be processed are called “zero-sampling”; specifically, are all NOP, JUMP, LOOP and END sectors.
A sector zero sampling is also considered the codeG = 133 se programmato come:

• codeG = 133
• codeQm = 0
• codeQs = 0

It is not possible to sequence more than 9 zero sampling areas.

The update count is used to make an exchange of the count, to values that may indicate the actual physical location of the axis. The most typical case is the circular axis (from 0° to 360°): whenever you reach 360° you must subtract a circle. To make an update count there are multiple codes of subtraction or bit encoder count setting, whether that unit of measure. For how it is structured the device, it is not possible to sequence more than 4 sectors count update. The following table containing the description of what happens during the update count based on the code used.

codeG Execute operations
139 Subtraction by count master value contained in the codeQm (expressed in units of measurement).
Subtraction from the slave count value contained in codeQs (expressed in units of measurement).
140 Forcing master count to the value that is contained in codeQm (expressed in units of measurement).
141 Forcing the slave to the count value in codeQs (expressed in units of measurement).
142 Forcing master count to the value that is contained in codeQm (expressed in units of measurement).
Forcing the slave to the count value in codeQs (expressed in units of measurement).
143 Subtracting the value contained in the master count codeQm (expressed in bit encoder multiplied by 4).
Subtracting the slave count value contained in codeQs (expressed in bit encoder multiplied by 4).
144 Forcing master count to the value that is contained in codeQm (expressed in bit encoder multiplied by 4).
145 Forcing the slave to the count value in codeQs (expressed in bit encoder multiplied by 4).
146 Forcing master count to the value that is contained in codeQm (expressed in bit encoder multiplied by 4).
Forcing the slave to the count value in codeQs (expressed in bit encoder multiplied by 4).

As an example, consider a simple wire-guides:

• Starting with acceleration ramp.
• Achieving a speed proportional to that of the master.
• Maintenance of speed for the entire journey.
• Stop with deceleration ramp.
• Stop the axis for some space of the master.
• Return to the starting point with the same stroke mode.

Sector 1 Acceleration, from zero speed and positive shift slave (codeG = 131). It is important to calculate the ratio of space master/slave of this section so that the output speed is the one that will be maintained by the slave axis in the stretch at constant speed.

Sector 2 Intermediate with constant speed and positive shift slave (codeG = 133).

Sector 3 Deceleration with final zero speed, with a possible braking speed compensation in the first half of the stroke and the slave positive displacement (codeG = 135). May have the same values set in the field 1.

Sector 4 Stop working with slave zero shift (codeG = 133). Programming master space while the slave is set to 0.

Sector 5 Acceleration, from zero speed and negative shift slave (codeG = 131). It is important to calculate the ratio of space master/slave of this section so that the output speed is the one that will be maintained by the slave axis in the stretch at constant speed. Ideally, you can use the same values entered in the sector 1 changing the quota sign slave.

Sector 6 Intermediate with constant speed and negative shift slave (codeG = 133).

Sector 7 Deceleration with final zero speed, with a possible braking speed compensation in the first half of the stroke and negative shift slave (codeG = 135). May have the same values set in the sector 5.

Sector 8 Stop working with slave zero shift (codeG = 133). Programming master space while the slave is set to 0. After you run the sector 8, there must be some functions that perform power factor correction of Master and Slave counters by subtracting the space covered until the end of the sector; then you will have to have the automatic replay same cam from sector 1 (JUMP or loop cam).

As an example, consider a simple fly cut:

• Start slave axis with acceleration ramp.
• Achievement of the master speeed.
• Maintaining the speed reached throughout the cut.
• Finished cutting, the slave axis must accelerate to go to go to an extra speed, keeping it for a certain space.
• Stop slave axis with deceleration ramp.
• Return of the slave axis to the starting point (home), without inversion time and following the acceleration and deceleration ramps.

Sector 1 Acceleration, with starting from zero speed and positive shift slave (codeG = 132). At the end of this sector the slave will have the same speed of the master.

Sector 2 Intermediate with constant speed and positive shift slave (codeG = 133). In this area the space covered by the master is the same as the path from the slave.

Sector 3 Positive acceleration and displacement slave (codeG = 133). The code set rule slave acceleration than the master, it sets a space more than the master.

Sector 4 Intermediate with constant speed and positive shift slave (codeG = 133). In this area the space covered by the slave will be proportion to that route from the master.

Sector 5 Deceleration and positive shift slave (codeG = 133). In this sector takes the slave at the same speed as the master.

Sector 6 Deceleration with final zero speed, with a possible braking speed compensation in the first half of the stroke and the slave positive displacement (codeG = 135).

Sector 7 Acceleration, with starting from zero speed and negative shift slave (codeG = 131). In this area the output speed of the slave may differ from that of the master.

Sector 8 Intermediate with constant speed and negative shift slave (codeG = 133).

Sector 9 Deceleration with final zero speed, with a possible braking speed compensation in the first half of the stroke and negative shift slave (codeG = 135).

After you run the sector 9, there must be a function that performs the power factor of the counter of the Master, subtracting the space covered until the end of the field and, subsequently, automatically resubmitting the same cam (JUMP or loop cam).

A bug in the system camming is reported by the st_error state.
Being caused by a serious event and not being guaranteed in this situation the slave axis management, It was decided arbitrarily to block the axis without ramps as had taken place an emergency.
When st_error is equal to 1, are present on the errcode variable the type of error occurred (see the table) and in errvalue variable an indication on the cause of the error.

If the device goes in error, in order to start cut you have to clear the st_error status through RSERR command and then the usual routine of emergency recovery (RESUME axis).

NOTE: Error 4 is due to the fact that the sector is run in a time less than the sampling time of the device, so it cannot be tried. If you are in this situation you have to increase the share of the master in the sector, or lower the speed of the master.

The presence of a warning system camming is signaled by the st_warning state.
Being caused by a minor event and being guaranteed in this situation the slave axis management, the slave axis continues his work.
When st_warning is equal to 1, are present on the wrncode variable the type of warning intervened (see the table) and in the wrnvalue variable the sector number of the cam that caused the warning.

The highest priority is marked from 0, the lowest with 8.
To clear the st_warning status must send the RSWRN command.
NOTE: In case of warning 8, the function will be delayed long enough to allow the CPU to terminate the internal calculations. In the case of cam start from the interrupt input, the startup location cam can not be that of the moment of interrupt, but that after the end of the calculations. The execution time of calculations (expressed as sampling time of the device), is shown in the following table:

	The encoder device master of CAMMING2 is in no way linked to the encoder EANPOS device.

The device CAMMING2 can handle two types of master:

• Both may be coming from an encoder mechanically connected to the master system and electrically connected to the system QMOVE or simulated encoder. It also accepted the mixed solution (one connected electrically and one simulated). The exchange between the two encoder is done through the parameter mtype without any constraint, so that even in the execution of a cam, you can make the exchange between devices. On your system using the device CAMMING2 can be declared a simulated encoder using a device of movement (for example the EANPOS) declared with the counter on slot 1 (normally reserved to the CPU of the system) and any other disable devices:

;-----------------------------
; Dichiarazione device interni
;-----------------------------
 
INTDEVICE
<device_name>   EANPOS   TCamp   ICont   IntL   IAZero   IOutA
Master          EANPOS   2       1.CNT01 X      X.X      X.X

where:

The device thus configured as a simulated master and is parameterized and used like a normal device bearing in mind that the control loops must be open (st_loopon = 0) and therefore don't need to parameterize the P.I.D. but just set the feedforward to 100% (feedfw = 1000).

We use the EANPOS device configured as in the previous example, and you want to give the set of speed (setvel) expressed in Hz. It is assumed that the master simulated should continue its movement ad infinitum.
The sf01 flag for the start and stop simulated device.

;----------------------------------------------------
; Simulated master management
;----------------------------------------------------
 
Master:measure = 1000
Master:pulse = 4000
Master:decpt = 0
Master:unitvel = 1
Master:maxvel = 1000
Master:taccdec = 100
Master:maxpos = 999999
Master:minpos = -999999
INIT Master
WAIT Master:st_init
LOOPOFF Master
WAIT NOT Master:st_loopon
RESUME Master
WAIT NOT Master:st_emrg
 
MAIN:
IF sf01
  IF Master: st_still
    Master:posit = 0
    Master:setvel = 500
    Master:setpos = 999999
    START Master
  ENDIF
  IF Master:posit GE 500000
    Master:posit = 0
  ENDIF
ELSE
  IF NOT Master:st_still
    STOP Master
  ENDIF
ENDIF
 
WAIT 1
JUMP MAIN
END

To have a proper functioning during synchronisation, It is required that the pulses in the time (frequency) generated from ther Master transducer are greater or equal to those of the Slave axis. In any case you are required to comply with the condition

Slave frequency = 1,5 × Master frequency

In the case of a failure to comply with this condition will cause trouble in the calibration of the Slave axis in synch because of a roughness in the movement.

The device has the ability to manage a normal entrance and an interrupt input to run commands or perform actions. The address of the inputs can be setting in the configuration file (InG and InGInt). To perform a specific function at the entrance, simply assign at the funInp variable (If this is the normal input) or funInt variable (If this is the interrupt input) the code listed in the following table.

All functions of the inputs can be handled either on normal inputs on interrupt inputs.
To have a correct operation of the inputs, they are enabled by respecting the conditions set out in the description of the command or action described.

The device has the ability to handle an exit to signal certain states. The address of the output can be setting in the configuration file (Out). To perform a specific function on output, simply assign the variable funOut code shown in the following table.

The parameter name, condition or command is taken back to the left of the table

=R\\=

Indicates whether its parameter or state is retentive (upon initialization of the device maintains the previously defined), or the state assumes upon initialization of the device.
R = Retentive
0 = Upon initialization of the device the value is forced to zero.
1 = Upon initialization of the device the value is forced to one.

=D\\=

Indicates the size of the parameter.
F = Flag
B = Byte
W = Word
L = Long

Describes all the conditions necessary so that the parameter is considered correct or because the command is accepted.
In some cases, limit values are specified for the acceptance of the parameter: If any values outside the limits set, the data is anyway accepted; so they should be provided appropriate internal controls to ensure the proper functioning. To run a command, all the conditions must be met; otherwise the command does not run.

A

Indicates the access mode.
R = Read.
W = Write.

1. Non è possibile mettere in sequenza più di 7 settori a campionamento zero.
2. Non è possibile mettere in sequenza più di 3 settori di aggiornamento conteggio.
3. Con i parametri:
   pulse = 999999
   measure = 934
   maxvel = 999999
   unitvel = 0
   decpt = 3
   Si stabiliscono le condizioni per creare degli overflow nei calcoli dei settori 150, 151, 152 e 153.
4. Durante l’esecuzione della camma (st_camex = 1), non è possibile cambiare il settore in esecuzione e quello eseguito successivamente.
5. Il device è stato creato per funzionare con il master che si incrementa. E’ possibile eseguire la camma con il master che decrementa sottostando alle seguenti condizioni:
   La camma si ferma rimane in reazione di spazio sul settore precedente se incontra i settori 130, 137, 138, 139, 140, 141, 142, 143, 144, 145, 146, 160. Può eseguire il settore precedente solamente se è già stato eseguito almeno una volta (potrebbe non essere stato eseguito a causa di un jump).